System and method for synchronizing bi-directional document management

ABSTRACT

Systems and methods consistent with various disclosed embodiments provide for collaborating information over a computer network. In one embodiment, a system is disclosed for collaborating information over a network. The system may include a storage device and one or more processors. The processor(s) may maintain documents in the storage device and publish content links to the documents in a workspace rendered by a collaboration platform. The processor(s) may provide content to the collaboration platform in response to a content link selection by a reviewer and receive the reviewer&#39;s changes, with the collaboration platform temporarily storing the document in a virtual memory for rendering to the reviewer and deleting it after the communication session ends. The processor(s) may synchronize the changes bi-directionally from the workspace with the original document through a collaboration document, such that the original document remains unaltered, and by re-publishing an updated content link to the workspace.

FIELD OF THE INVENTION

Embodiments of the present invention generally relate to distributedcomputing systems and, more particularly, relate to systems, methods,and articles of manufacture for collaborating information over acomputer network.

BACKGROUND OF THE INVENTION

The ubiquity and versatility of the Internet continues to spur thedevelopment of information management applications. Software productssuch as HyperOffice, Dropbox, BOX, and OpenText Tempo™ provide userswith the ability to save and share documents in a Web (cloud) basedstorage container here they and other invited users can access thesedocuments. In such products, a user may select and save a copy of adocument from storage locations on their local computer or network orDocument Management System (DMS) to a container located on the Web,where they can later access it from any device over the Internet orshare it with others.

While such products provide remote access to documents, and consumerlever users find this functionality useful, they do not provide enoughversatility and security needed for business professionals sharinginformation on the Internet. Security, risk and compliance professionalsshy away from “documents in the cloud”. For example, conventionalsystems do not allow for the option for a document owner to send to areviewer only a link to a document that allows a reviewer limited accessto the document during a session with the Web-based service. Nor do suchsystems prevent the reviewer from maintaining a copy of the documentafter the session ends. Such systems further do not offer options forcollaborating on project folders that offer reviewer-specific access todocuments in the folders.

Accordingly, there is a need for a method and system that providescollaboration between information owners and reviewers while enablingowners to maintain control over original documents.

SUMMARY OF THE INVENTION

The disclosed embodiments provide, among other things, improved systemsand methods of collaborating information over a computer network.

In one embodiment, a system is disclosed for collaborating informationover a network. The system may include a storage device and one or moreprocessors. The one or more processors may maintain a document in thestorage device, the document being a copy of an original documentcreated by an owner and stored in a data storage separate from thestorage device. The one or more processors may also publish contentlinks to the document in a workspace that is configured by the ownerwith access rights for a first reviewer. The one or more processors mayadditionally provide content of the document to a collaboration platformin response to a selection by the first reviewer of the content link inthe workspace that is rendered by the collaboration platform to thefirst reviewer. The one or more processors may also receive, from thecollaboration platform, adjustments to the content made by the firstreviewer through the collaboration platform during a communicationsession with the collaboration platform, with the collaboration platformtemporarily storing the document in a virtual memory for rendering thedocument to the first reviewer during the collaboration session betweenthe first reviewer and the collaboration platform, and with thecollaboration platform also deleting the content from virtual memory inresponse to the first reviewer ending the communication session with thecollaboration platform. The one or more processors may furthersynchronize the adjustments to the document with the data storagethrough a collaboration document created by the data storage thatmaintains the adjustments to the document made by the first reviewersuch that the original document remains unadjusted. In addition, the oneor more processors may also create and maintain a second version of thedocument that includes the adjustments by the first reviewer andre-publish the content link to the document in the workspace such thatthe content link links to the second version of the document,bi-directionally synchronizing the content between the data storage andthe content links in the workspace rendered by the collaborationplatform.

In another embodiment, a system is disclosed for collaboratinginformation over a network that may include a data storage storing anoriginal document created by an owner, an application executed by aprocessor, and an agent server. The application may be configured toprovide a process for the owner to create a workspace and create anotification relating to the workspace relating to the workspace. Theagent server may be configured to create a second document that is acopy of the original document, assign access rights to the seconddocument for the one or more reviewers, and publish a content link tothe second document in the workspace. The agent server may also providecontent of the second document to a collaboration platform in responseto a selection, by the one or more reviewers, of the content link in theworkspace that is rendered by the collaboration platform to the one ormore reviewers during respective communication sessions between the oneor more reviewers and the collaboration platform. The agent server mayadditionally receive from the collaboration platform informationreflecting a change, annotation, and/or comment to the second documentmade by the one or more reviewers through the collaboration platformduring the respective communication sessions with the collaborationplatform, with the collaboration platform deleting the second documentfrom a virtual memory that is used for rendering the second document tothe one or more reviewers in response to the one or more reviewersending the respective communication sessions with the collaborationplatform. The agent server may also synchronize the change, annotation,and/or comment to the second document with the original document storedin the data storage.

In another embodiment, a system is disclosed for collaboratinginformation over a network that may include a virtual memory and one ormore processors that may be configured to receive a workspace from anowner, where the workspace includes a content link to a document createdby the owner. The one or more processors may also receive a request froma first reviewer to access the workspace and receive a selection of thecontent link from the first reviewer during a communication session withthe first reviewer over a network. The one or more processors may alsoretrieve, based on the selection, content for the document from theowner, store the document content in the virtual memory, and render thecontent from the document such that the first reviewer is able to accessand make changes to the document over the network based on access rightsto the document set by the owner. Additionally, the one or moreprocessors may receive input to the content from the reviewercorresponding to changes, annotations, and/or comments to the documentand provide the changes, annotations, and/or comments to the owner suchthat the owner synchronizes the changes, annotations, and/or commentsthrough a collaboration document that is separate from an originalversion of the document stored at a data storage. Further, the one ormore processors may delete the document content from the virtual memorywhen the communication session with the first reviewer ends.

In another embodiment, a system is disclosed for collaboratinginformation between an owner of a workspace and reviewers that mayinclude a virtual memory and one or more processors that may beconfigured to generate, for each reviewer, a customized view of theworkspace based on access rights set by the owner for each respectivereviewer. The one or more processors may also generate a content link toa document in the workspace that, when selected by a respectivereviewer, retrieves content relating to the document from an agentserver of the owner and temporarily renders the document to thereviewers using the virtual memory that prevents the reviewers fromretrieving a copy of the document. The one or more processors mayfurther be configured to send to the agent server information relatingto transactions performed on the document by authorized reviewers havingaccess rights to perform the transactions, and delete the document fromthe virtual memory after the transactions have been synchronized with anoriginal version of the document created by the owner.

In another embodiment, a process is disclosed for collaboratinginformation over a network. The process may include maintaining adocument in a storage device, with the document being a copy of anoriginal document created by an owner and stored in a data storageseparate from the storage device. The process may also includepublishing a link to the document in a workspace that is configured bythe owner with access rights for a first reviewer and providing contentof the document to a collaboration platform in response to a selection,by the first reviewer, of the content link in the workspace that isrendered by the collaboration platform to the first reviewer. Theprocess may further include receiving from the collaboration platformone or more changes to the document made by the first reviewer throughthe collaboration platform during a communication session, with thecollaboration platform temporarily storing the document content in avirtual memory for rendering the document to the first reviewer duringthe communication session with the collaboration platform, and thecollaboration platform deleting the document content from the virtualmemory in response to the first reviewer ending the communicationsession with the collaboration platform. The process may additionallyinclude synchronizing one or more changes to the document with the datastorage through a collaboration document created by the data storagethat maintains the one or more changes to the document made by the firstreviewer, with the original document remaining unchanged.

In another embodiment, a process is disclosed for collaboratinginformation over a network. The process may include receiving aworkspace from an owner, with the workspace including a content link toa document created by the owner. The process may also include receivinga request from a first reviewer to access the workspace, receiving aselection of the content link from the first reviewer during acommunication session with the first reviewer over a network, andretrieving, based on the selection, content for the document from theowner. The process may also include storing the document content in avirtual memory and rendering the content from the document such that thefirst reviewer is able to access and make changes to the document overthe network based on access rights to the document set by the owner. Theprocess may further include receiving input to the content from thereviewer corresponding to changes, annotations, and/or comments to thedocument and providing the changes, annotations, and/or comments to theowner such that the owner synchronizes the changes, annotations, and/orcomments to the document through a collaboration document that isseparate from an original version of the document stored at a datastorage. The process may additionally include deleting the documentcontent from the virtual memory when the communication session with thefirst reviewer ends.

In another embodiment, a process is disclosed for collaboratinginformation over a network. The process may include creating aworkspace, sending a notification relating to the workspace to one ormore reviewers, creating a second document that is a copy of an originaldocument stored in a data storage, and assigning access rights to thesecond document for one or more reviewers. The process may also includepublishing a content link to the second document in the workspace andproviding content of the second document to a collaboration platform inresponse to a selection by one or more reviewers of the content link inthe workspace that is rendered by the collaboration platform to one ormore reviewers during respective communication sessions between the oneor more reviewers and the collaboration platform. Additionally, theprocess may include receiving information from the collaborationplatform reflecting changes, annotations, and/or comments to the seconddocument made by one or more reviewers through the collaborationplatform during the respective communication sessions, with thecollaboration platform deleting, in response to the one or morereviewers ending the respective communication sessions with thecollaboration platform, the second document from a virtual memory thatis used for rendering the second document to the one or more reviewers.The process may further include synchronizing the changes, annotations,and/or comments to the second document with the original document storedin the data storage.

In another embodiment, a system is disclosed for collaboratinginformation over a network that may include a storage device and one ormore processors. The one or more processors may bi-directionallysynchronize content included in an original document created by an ownerand the document's content rendered on a workspace provided by acollaboration platform using a copy of the original document that isstored in the storage device, with the workspace being accessible by oneor more reviewers over a network. The one or more processors may alsosynchronize each reviewer's adjustments made to the document's contentin the workspace with the content in the original document such thateach reviewer can view the adjustments to the document's content made byother reviewers through the workspace during respective communicationsessions with the collaboration platform.

Additional objects and advantages of the disclosed embodiments will beset forth in part in the description which follows, and in part will beobvious from the description, or may be learned by practice of thedisclosed embodiments. The objects and advantages of the disclosedembodiments will be realized and can be attained by the elements andcombinations particularly pointed out in the appended claims.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed and/or claimed embodiments.Further features and/or variations may be provided in addition to thoseset forth herein. For example, the disclosed embodiments may be directedto various combinations and subcombinations of the disclosed featuresand/or combinations and subcombinations of several further featuresdisclosed below in the detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate various embodiments and aspectsof the present invention. In the drawings:

FIG. 1 illustrates an exemplary system environment for implementingcertain embodiments;

FIG. 1A illustrates an exemplary workspace for implementing certainembodiments;

FIG. 2 illustrates an exemplary client system implementing certainembodiments;

FIG. 3 is a flowchart illustrating an exemplary workspace creationprocess consistent with certain disclosed embodiments;

FIG. 3A is a diagram of an exemplary system environment for implementingcertain embodiments;

FIG. 4 is a flowchart illustrating an exemplary workspace update processconsistent with certain disclosed embodiments;

FIG. 5 is a flowchart illustrating an exemplary collaboration reviewprocess consistent with certain disclosed embodiments;

FIG. 6 is a flowchart illustrating an exemplary synchronization processconsistent with certain disclosed embodiments;

FIG. 7 is a diagram of an exemplary system environment relating toreviewer collaboration processes consistent with certain disclosedembodiments; and

FIG. 8 is a diagram of an exemplary system environment relating tocollaboration synchronization processes consistent with certaindisclosed embodiments.

DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to the exemplary embodiments of theinvention, examples of which are illustrated in the accompanyingdrawings. Wherever possible, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

FIG. 1 illustrates an exemplary system environment 100 consistent withcertain disclosed embodiments. In one example, system 100 provides acollaboration environment where client systems 102, 104 are connected toa network 120 and can share and make changes to, comment on, andannotate information via a collaboration platform 110. In certainembodiments, system 100 enables a user to share information by, forexample, synchronizing documents created by one or more clients 102, 104with collaboration platform 110 and providing access to those documentsvia collaboration platform 110 through links to the documents inaccordance with certain embodiments of the present invention.

Client 102,104 may be a computer system including one or more computingcomponents for performing one or more processes consistent with certainaspects of the disclosed embodiments. In one embodiment, client 102, 104may include one or more computer or data processing devices that havehardware (e.g., one or more processors, storage memory, data buses,network interface, etc.), software (e.g., web browsers, applicationprograms, operating systems, other executable program code written inany known programming language such as PL/SQL, AJAX, XML, JavaScript™,C, C++, Java™, etc.), and/or firmware (e.g., software embedded in ahardware device). Client 102, 104 may be configured to communicate withone or more networks, such as network 120, and with other clients orservers connected to network 120 or other computers or componentsconnected to a local network (not shown). One or more users may operateone or more components of client 102, 104 to perform one or moreprocesses consistent with the disclosed embodiments. Also, client 102,104 may be associated with an entity, such as a company, organization,government agency, educational or medical facility, firm, or any othertype of business or non-business entity. In certain embodiments, client102 may be associated with an entity that is different from thatassociated with client 104. Alternatively, client 102 and client 104 maybe associated with the same entity. Further, client 102 may beassociated with a department, division, etc. of an entity that isdifferent from a department, division, etc. of the same entityassociated with client 104. Moreover, client 102, 104 may executesoftware processes stored on tangible and non-transitorycomputer-readable mediums that perform one or more processes consistentwith the disclosed embodiments. While FIG. 1 illustrates two clients102,104, aspects of the disclosed embodiments are not limited to such aconfiguration. Thus, the disclosed embodiments may be implemented withany number of clients interconnected by network 120. Further, the term“client” used herein to describe client 102, 104 is not intended to belimiting to a client in the sense of known client-server configurations,although such configurations may be implemented by the disclosedembodiments. For example, client 102, 104, may be (or include) a servertype computer system or server software that may also request andreceive information, data, services, processes, etc. from anothercomputer system in a local and/or remote network.

In one embodiment, client 102, 104 may create, maintain, edit, modify,copy, send, receive, store, delete, and the like, one or more documents.In one non-limiting example, a document may be a file, email, calendar,articles, or other content or information that software, processors,and/or users may use. For example, a document may be a word processingdocument containing content (e.g., text, graphics, links, etc.). Adocument may also be a spreadsheet file, a web page, a PDF file, or anyother type of file that includes content that may be viewed, edited,modified, copied, shared, etc. by a user, processor, or software. Adocument may be included in a folder containing multiple documents. Forexample, disclosed embodiments may work with one or more folderscontaining one or more documents, such as multiple word processingfiles, spreadsheets, tables, graphical files, etc. A folder may alsoinclude one or more subfolders, each containing one or more documents.The above-listed examples of documents and folders are not intended tobe limiting to the disclosed embodiments.

In one embodiment, client 102, 104 and their respective user(s) (orentity associated with client 102, 104) may be an owner or a reviewer.For example, an owner may be a user or client that creates, maintains,controls, or otherwise is an owner of a document or a folder thatcontains multiple documents or subfolders. An owner may share one ormore documents or the entire folder through collaboration platform 110in accordance with certain disclosed embodiments. An owner may alsoedit, modify, delete, and copy a document that is owned by the owner.For example, an owner may create a word processing document using client102, 104 and have access rights to view, modify, and otherwise alter thecontents of that document in accordance with the disclosed embodiments.Aspects of the disclosed embodiments may also allow another user to haveowner rights to that document. A client, such as client 102, may be usedby one or more owner users to create, modify, copy, delete, and/or shareone or more documents, and thus may also be an owner. A reviewer may bea user or client that accesses, reviews, analyzes, modifies, commentson, annotates, edits, or otherwise works with a document shared by anowner in accordance with certain disclosed embodiments. For example,client 102 (and/or a user of client 102) may be an owner and client 104(and/or a user of client 104) may be a reviewer of documents and/orfolders shared by client 102. Further, client 102 may be a reviewer ofdocuments and/or folders shared by client 104. Other clients (not shown)may also be implemented that each may be owners, reviewers, or both,respective to other clients.

In certain embodiments, an owner of a document may be a reviewer ofanother document and/or folder, and the reviewer of a document and/orfolder may be the owner of another document and/or folder. For example,client 102 may be an owner of a word processing document created by auser associated with client 102 that is configured to share thatdocument with client 104 through collaboration platform 110. In thisexample, client 104 may be a reviewer of the word processing documentshared by client 102. Client 104 may also be an owner of a spreadsheetdocument that is shared with client 102 through collaboration platform110. In this example, client 102 is an owner of the word processingdocument and a reviewer of the spreadsheet document, while client 104 isan owner of the spreadsheet document and a reviewer of the wordprocessing document.

In certain embodiments, any number of clients (and users) may sharedocuments using collaboration platform 110. Thus, owners and reviewersmay be individuals or groups of individuals with access to thecollaboration platform 110 using client 102, 104. A document may haveone or more owners, and may be accessible by one or more reviewersdepending on various determined user authorizations and access rights.Certain embodiments enable an owner to establish access rights that willallow viewing, annotating, or editing of the documents by one or morereviewers. Further, embodiments enable an owner to prevent one or morereviewers to retain copies of the owner's document, enabling the ownerto retain complete control over their document. In other embodiments,owners may grant varying levels of access rights to reviewers, such thatcertain reviewers may alter or gain control over certain shareddocuments or underlying information, files, content etc. in a document.

Referring back to FIG. 1, network 120 may be any type of communicationnetwork configured to communicate information in system 100. Network 120may be a wireless and/or wireline network including one or morecomponents (e.g., hardware, software, and/or firmware) configured toreceive, route, translate, and deliver information. For example, network120 may be the Internet, an Extranet, an Intranet, a Local Area Network,Wide Area Network, etc. that enables clients (or other computer systems)to communicate and collaborate in accordance with aspects of thedisclosed embodiments. Network 120 may include infrastructure thatimplements the communication and collaboration of information over thesetypes of networks, such as routers, bridges, servers, wireless/wirelinebase stations, transceivers, and related technology. In certainembodiments, network 120 may be separate networks that connect client102 to collaboration platform 110 and that connect client 104 tocollaboration platform 110. For example, network 120 may include a localarea network, wide area network, portions of the Internet etc. thatprovide connections between client 102 and collaboration 110 that isdifferent (in whole or in part) to a local area network, wide areanetwork, portions of the Internet etc. that provides connections betweenclient 104 and collaboration 110.

Collaboration platform 110 may be a system that provides collaborationand other types of information sharing processes consistent with thedisclosed embodiments. In one example, collaboration platform 110 may bea web-based computing system that interconnects with one or moreclients, such as clients 102, 104, over the Internet. In one example,collaboration platform 110 may include one or more servers and memorystorage devices. For instance, collaboration platform 110 may includeone or more computer or data processing devices that have hardware(e.g., one or more processors, storage memory, data buses, networkinterface, etc.), software (e.g., web browsers, web servers, applicationprograms, operating systems, other executable program code written inany known programming language such as PL/SQL, AJAX, XML, JavaScript™,etc.), and/or firmware (e.g., software embedded in a hardware device).Collaboration platform 110 may also include one or more memory devices,such as local or networked memory storage media, shared memoryplatforms, or a combination thereof. In certain embodiments,collaboration platform 110 includes memory that stores documents,folders of documents, information, content, data, etc. for transmissionand viewing by clients 102, 104 through browser or similar type ofsoftware. In accordance with disclosed embodiments, collaborationplatform 110 temporarily provides access to such information in avirtual memory during communication sessions with a client (e.g., client102,104), and deletes the information from its virtual memory at the endof a communication session with the client.

Virtual memory may be a physical memory that is configured totemporarily store content (e.g., documents, folders, information, etc.)that is used by collaboration platform to provide the content toreviewers via browser software executed at the reviewer client computer.Collaboration platform 110 may be configured to delete the content whena communication session ends with the reviewer computer such that thereviewer computer does not retain copies of the content (including adocument) in temporary cache memory of the reviewer client computer'sbrowser. Thus, unlike typical web servers that may load content into atemporary memory on the server that is accessible by users after acommunication session ends with the users, collaboration platform 110may use a virtual memory dedicated to store content and informationassociated with an owner's document and/or folder that is deleted aftercommunication sessions end with users accessing that content andinformation.

Collaboration platform 110 may be configured to execute software thatperforms processes consistent with the disclosed embodiments. Forexample, collaboration platform 110 may perform security processes thatcontrol access to documents, folders of documents, or any otherinformation that may be temporarily displayed and processed bycollaboration platform during a communication session with one or moreclients 102, 104. Collaboration platform 110 may also performcollaboration processes that enable clients 102, 104 (or their users) toshare and collaborate on documents, folders of documents, content, orother information over network 120. Collaboration platform 110 may alsoperform processes that enable users or clients to communicate via, forexample, email or instant messaging. In certain disclosed embodiments,collaboration platform 110 may also provide application specificoperations, such as content viewer, editor, collaboration, sidebar,approval, compare, clean metadata, PDF-creating, reporting, and/oradministrative applications, calendar, and security functions.Collaboration platform 110 may also execute software that allowsmultiple clients or their users to simultaneously log-in and interactthrough hosted communication applications, such as instant messaging orother real-time communications functions. Collaboration platform 110 mayalso provide message boards, private messaging, wall postings, email,and various other methods of electronic communication known in the art.

In certain embodiments, collaboration platform 110 performs processesthat may display content links to shared content, including data,documents, folders, and other information through a workspace. In oneexample, a workspace may be a virtual environment hosted bycollaboration platform 110 that facilitates collaboration and sharingamong owners and reviewers. A workspace may be customized by users ofclients 102, 104 to display customized information over network 120during communication sessions between collaboration platform 110 andclients 102, 104. Workspaces may be created by a client (e.g., client102, 104) via user input. In one embodiment, a user who creates aworkspace may configure user authorizations and access rights to permitowners to share documents, folders, content, etc. and to permitreviewers to access and possibly edit that information on the workspace.Collaboration platform 110 may be configured to render content linkswithin a workspace that, when selected by a client owner or reviewer(102, 104), retrieve content and information associated with documentsand folders from a client owner for rendering the requested content andinformation in a viewer, editor, or a web-based tool that enables usersto view and possibly edit, annotate, or otherwise change information inthe content. A workspace may further enable owners to configure userauthorizations and access rights for each content link, enabling ownersto exercise control over their documents, folders, or content. Inaccordance with certain disclosed embodiments, owners may publish linksto content on the workspace through, for example, a content sharingprocess described below.

In certain embodiments, a workspace may be configured to include areasthat are designated for certain features and for owners or reviewers. Inone example, a workspace may include display tabs, menus, dashboardelements, and/or graphical displays for providing email, calendar, news,history, reporting, activity logs, instant messaging, message boards,links to other workspaces, and analytics such as expenses and billingfor rendering information relating to specific tasks, matters, projects,or features. In further embodiments, a workspace may also include customtabs, menus, elements, dashboards, and/or graphical displays created andconfigured by a user (or client) that created the workspace, or by otherauthorized users (or clients) with access rights to configure theworkspace.

Owners may create their own workspaces and reviewers may, if authorized,add documents, content, etc. to be included in an owner's workspace.Workspace views may be customized and dictated by user access rights,such that documents, folders, content, and browser menu options will orwill not be available in accordance with user access rights, such asblocking save as or print options if specific rights have not beengranted. In one embodiment, for example, a user may initiate a requestat client 102 to create a new workspace. Client 102 may performprocesses that enable the user to configure owner/reviewer rights to theworkspace, select documents, folders, content etc. that are to beincluded in the workspace, and set authorizations and access rights forsome or all of the documents, folders, and content associated with theworkspace. The user may therefore authorize only certain users—ownersand reviewers—to access the new workspace, and may grant differentlevels of access to the links to documents, folders, and contentincluded in the workspace among the authorized users. For example, auser may authorize certain reviewers to have access to review—but notedit—selected documents, while permitting other reviewers to both reviewand edit those same documents. In a further embodiment, an owner maypermit certain reviewers only temporary access to review and/or editshared content provided by collaboration platform 110, but permit otherreviewers to retain and save copies of the shared content. Throughvarious disclosed embodiments, owners may grant reviewer authorizationsand varying levels of access in order to, for example, retain controlover their shared content, or to permit certain reviewers to alter thatcontent, or to permit certain reviewers to retain and save copies ofthat content. In another embodiment, collaboration platform 110 may beconfigured to perform access control rules that adhere to Country dataprivacy restrictions that prevent access to any information outside ofrestricted Countries.

FIG. 1A illustrates an exemplary workspace 150 that collaborationplatform may provide in accordance with certain disclosed embodiments.Workspace 150 may be a workspace that an owner has configured specificaccess rights to information for a reviewer to access, view, andpossibly annotate and/or edit. Exemplary workspace 150 may include afolders area 151 that lists folders of documents that the reviewer isauthorized to view and access. Workspace 150 may also include a documentlist area 152 that lists one or more content links (e.g., content links1 to N) to accessible documents included in a selected folder from thefolders area 151. A reviewer may access a particular document byselecting an appropriate link listed in the document list area 152 ofworkspace 150. In one example, document list area 152 may include fields161 that present characteristics of each document affiliated with acontent link. For instance, FIG. 1A shows a “From” field that mayidentify the owner of a document relating to each content link. The“Document Name” field may include the content link including a name ofthe document. The “Last Updated” field may represent when the underlyingdocument of each content link was last updated through collaborationplatform 110. The “Status” field may represent the current status of theunderlying document for each content link. For example, a document maybe in an unreviewed status, meaning the document has not been reviewed,an under review status, meaning the document is being reviewed, or areview complete status, meaning the document review is complete. Otherstatus identifiers and other fields 161 may be implemented withoutdeparting from the scope of the disclosed embodiments.

Workspace 150 may further include a document list area for approved orfinal versions of documents that provide links to access documents butprovide no editing or altering functionalities for those documents.Workspace 150 may also include an area 155 that provides otherinformation, such as a calendar that provides a calendar view of itemsrelated to a particular matter that the reviewer has been authorized toview or edit.

Workspace 150 may also include an assigned entity area 153 that includesinformation relating to the entity that is assigned rights to workspace150. Workspace 150 may also include an assigned users area 154 thatincludes names or identifiers of one or more users assigned certainrights to workspace 150.

Thus, in certain embodiments, a workspace may be an informationconfiguration that includes content links to documents and folders.Access to the documents and folders of workspace may be customized suchthat when rendered by collaboration platform 110, the workspace maypresent only information and content (e.g., content links to folders anddocuments, tabs, elements, etc.) that are authorized for access byassigned users. For example, a workspace may be configured to includeFolder 1 and Folder 2 (shown in FIG. 1A) and Content Links 1-3 (shown inFIG. 1A) for user 1 and user 2 (shown in FIG. 1A). Collaborationplatform 110 may be configured via aspects of the disclosed embodimentsto render the same workspace but with different content links for user 3(shown in FIG. 1A).

Other areas, information, tabs, elements, dashboards, etc. may beincluded in a workspace, and the example shown in FIG. 1A is notintended to be limiting to the disclosed embodiments. For example, in aworkspace generated for collaboration between a corporate client andlaw, workspace views may contain the following elements: a CorporationMatter/Project Folder Listing, Content Tab, Approved Content Tab, EmailTab, Legal Research Tab, News Tab, Team Contact Information, AttorneyProfile Information, Matter/Project/Content Calendar, History andReporting, Budgets, Expenses, etc. The Corporation Matter/Project FolderListing may display Matter Name and default sub-folders (e.g., General,Correspondence, Legal Hold). The Content Tab may display listing ofhyperlinks to content shared by content owners and reviewers. TheApproved Content Tab may also display listings of hyperlinks to finaland/or approved versions of documents and other content. Consistent withcertain disclosed embodiments, a workspace may provide an approvalfunctionality that, as one example, may enable users to publish links orsend notification emails to other users requesting approval, rejection,comments, or other feedback on a proposed final version of a document,and generate a link to a final version under the Approved Content Tab ifthe other users approve it. The Email Tab may display a listing ofhyperlinks to email threads initiated by content owner(s) and/orreviewer(s). The Legal Research Tab may display hyperlinks to legalresearch provided by content owner(s). The News Tab may displayhyperlinks to news articles provided by content owner(s). The TeamContact Information may display hyperlinks to both law firm attorney(s)and Corporate inside counsel assigned to a matter/project. Clicking onprovided hyperlinks may display attorney profile information. TheMatter/Project/Content Calendar may provide information in calendarformat that may be used to keep track of deliverables and due dates. TheHistory Tab may display connection history and hours worked on contentfor each team member. In one embodiment, this tab may only be visible tothe workspace creator. The Reporting Tab may display history of changesfor given content, documents, etc. This tab may also be configured toonly be visible to the workspace creator. The workspace 150, in certainembodiments, may further provide capabilities such as binder or reportfunctions that may assist a client 102, 104 in creating collections ofvarious information and linked content on the workspace 150. Consistentwith various embodiments of the disclosed invention, workspace 150 maybe a unified workspace providing comprehensive collaborationfunctionalities, including document-sharing, communication, scheduling,etc., between various users and entities in a variety of contexts.

FIG. 2 shows components of an exemplary client 102 consistent with thedisclosed embodiments. The illustration, descriptions, functionalities,and operations disclosed in connection with client 102 are alsoapplicable to client 104 (or other clients that may be implemented insystem 100). As shown, client 102 may include one or more client devices202, one or more client storages 204, and one or more agent servers 206.

Client device 202 may be one or more computer systems configured toexecute software, create, edit, modify, manage, etc, documents, and sendand receive documents. For example, client device 202 may be a desktopPC, a laptop, a PDA, a workstation, tablet, cell phone device, smartphone device, or any other processor, computer, or device (or groupthereof) configured to locally or remotely execute software, send andreceive information over a network, such as the internet, and performdata processing operations. In one embodiment, client device 202 mayinclude one or more computer or data processing devices that havehardware (e.g., one or more processors, storage memory, data buses,network interface, etc.), software (e.g., web browsers, applicationprograms, operating systems, other executable program code written inany known programming language such as PL/SQL, AJAX, XML, JavaScript™,etc.), and/or firmware (e.g., software embedded in a hardware device).

One or more users may operate client device 202 to perform functionsconsistent with certain embodiments of the disclosed invention. Incertain embodiments, client 202 may execute software that performsprocesses that access one or more client storage 204 and agent server206, and may also access collaboration platform 110 through a securedlayer, such as a firewall (not shown). In one embodiment, client devicemay include one or more client applications 202A, which may be softwareapplications that work with documents, data, content or other types ofinformation. For example, client application 202A may include a wordprocessing application, such as Microsoft Word™, a spreadsheetapplication, a document management system (DMS) client application, anemail application (e.g., Microsoft Outlook™), and/or a documentcollaboration application, such as Google Does, Zoho, or a Litera IDSclient. Client device 202 may include one or more client applications202A that provide different types of features, such as email, documentcreation and editing, document comparison, PDF processes such asprinting, extraction, redaction, Bates numbering, binding or editing,web-page related applications, graphical drawing applications, financialservice applications, etc without departing from the features of thedisclosed embodiments. In one embodiment, through client application202A, client 202 may host and provide one or more of the followingservices and capabilities: access rights selection, content viewer,content editor, collaboration, sidebar, content approval process,content compare and/or redline, calendar, email, reporting, andadministration.

In one embodiment, client application 202A may include the functionalityto create workspaces and invite reviewers to access documents or foldersin a workspace. For example, aspects of the disclosed embodiments enablea word processing application to include a “create workspace” optionsuch as a command that a user may select to create a workspace renderedby collaboration platform 110 during a collaboration session. The wordprocessing application may also include ribbons or hot-key combinationlogic that enables a user to initiate an invite to one or more reviewersto access and review a document created or changed using the wordprocessing application.

Client storage 204 may be one or more local or network memory storagemedia, or internal and/or external network-based document or datamanagement systems. For example, client storage 204 may include one ormore storage systems 204A that include one or more computer systems(e.g., database servers) and one or more tangible non-transitory storagemedia, such as one or more databases, hard drives or other types ofstorage devices. Storage system 204A may include, for example, adocument management system (DMS), such as SharePoint®, Desksite®,Autonomy iManage, OpenText Tempo™, WorldDox®, NetDocuments®, DropBox,Box.net or network storage. Client storage 204 may be configured toexecute one or more processes consistent with certain disclosedembodiments. In certain embodiments, storage system 204A may storeoriginal documents created by an owner user using client application202A executed by client device 202. Storage system 204A may also storeversions of original documents that may include changes made by theowner or one or more reviewers through collaboration platform 110. Incertain embodiments, client storage 204 may provide access to documentsand folders of documents through client device 202 and/or agent server206 to select data, documents, folders of data or documents, or othercontent to share over collaboration platform 110.

In certain embodiments, client storage 204 may store original documentscreated by owners and corresponding collaboration files that aredocument versions for any changes to an original document. In oneembodiment, the collaboration files are stored in a format that isdifferent from the format of the original document. As one example, anoriginal document may be created as a Microsoft Word™ document (e.g.,.docx file format), but the collaboration file for that originaldocument may be stored as a Litera IDS file (e.g., .ids file format)based on changes made using IDS editing tools during a collaborationsession. Client storage 204 may execute a stub-holder that pulls in anoriginal document from storage and compares all collaborative changescaptured during a collaboration session. Client storage 204 may alsostore an edit history table and a version control table that maintainhistorical information reflecting edits made to a particular documentand the versions of the document created based on those documents.

Agent server 206 may include one or more computers configured to executesoftware that performs one or more processes consistent with thedisclosed embodiments. Agent server 206 may be configured to performsynchronization functions with collaboration platform 110 and clientstorage 204 to maintain up to date versions of original documents,folders, and other content provided in workspaces. In certainembodiments, agent server 206 may be configured to function as atransitional content repository as an intermediary between client 102,104 and collaboration platform 110. In further embodiments, agent server206 may be configured to function as an interface to accesscollaboration platform 110. Thus, in certain embodiments, software,algorithms, web rendering logic, data, etc. used to provide applicationsmay reside in the collaboration platform 110, and not with agent server206. Agent server 206 may be configured to receive requests related toapplications, for example, from client device 202. Agent server 206 mayalso be configured to deliver requests to collaboration platform 110,and to receive application or application-related information fromcollaboration platform 110.

Although FIG. 2 shows client device 202, client storage 204, and agentserver 206 as separate components, the disclosed embodiments mayimplement single computer systems that operate as a client device 202,client storage 204, and agent server 206, or any combination thereof.

In one embodiment, agent server 206 may include one or more computer ordata processing devices that have hardware (e.g., one or moreprocessors, storage memory, data buses, network interface, etc.),software (e.g., web browsers, application programs, operating systems,other executable program code written in any known programming languagesuch as PL/SQL, AJAX, XML, JavaScript™, etc.), and/or firmware (e.g.,software embedded in a hardware device) that provide information to, andreceive information from, collaboration platform 110. Agent server 206may include one or more databases that maintain information and tablesfor managing and performing collaboration functions consistent with thedisclosed embodiments. For example, agent server 206 may include an edithistory table or activity log that maintains date and timestampinformation relating to a transaction associated with the creation orupdate of an original document stored in client storage 204. The edithistory table in the agent server may also include an identifier (e.g.,userid) of the client or user that initiated the transaction (e.g.,create or edit). Agent server 206 may also store=entries in its edithistory table to log an invitation generated by agent server 206 tonotify one or more reviewers of a transaction (e.g., document creationor edit). The invitation log data may include a date and timestamp ofthe transaction, and the identifier of the user or client that initiatedthe transaction. Agent server 206 may also create and maintain aninvitation table or log that stores an activity record of the emailaddress (or similar contact information, such as IP address, etc.) foreach recipient of the invitation that may be associated with theinvitation (e.g., email) record maintained in the edit history table.Alternatively or in tandem, collaboration platform 110 may also generateand store entries in an edit history table or activity log whenever atransaction occurs with a document or a content link.

Agent server 206 may maintain copies of documents and all collaborativechanges as separate data objects for document management and versioncontrol. The edit history and version controls may be bi-directionallysynchronized with the original document maintained by client storage 204and the content links published or re-published on the workspace 150. Incertain embodiments, agent server 206 executes software that providesthe functional logic to control: (1) database operations, includingcreation of user accounts, unique identifiers, global unique identifiersfor workspaces, activity logs and connection history; (2) content flowand distribution; (3) connection access and communication withcollaboration platform 110, client storage 204, client device 202, andother systems (e.g., client 104); (4) integrated security technologiesto secure connections and content within collaboration platform 110; (5)distribution and execution of application services and backendtechnologies (e.g., document processing, change management, spreadsheet,metadata management, etc.); and (6) integration with nativecontroller(s) to create and maintain user accounts.

Agent server 206 may also execute software that collects and maintainsinternal and external userids, including those based on email addresses,and also retrieves IP information when a user (e.g., an owner orreviewer) logs on to collaboration platform 110 to determine geographiclocation of the user. In one embodiment, agent server 206 may performprocesses that use the retrieved IP address to control and adhere toCountry specific data privacy restrictions, such that, for example,workspace views outside of a restricted Country will not be allowed. Forexample, agent server 206 may prevent a reviewer from the United Statesfrom viewing workspace documents that originated from an owner fromSweden based on governing laws that may prevent foreign users fromviewing certain information. In one aspect, agent server 206 maymaintain and execute one or more rules that analyzes Countryidentification information extracted from users' IP addresses when theylog on to collaboration platform 110 to determine whether to applyaccess restrictions to a workspace, or documents or content within theworkspace. Other types of geographical based access restrictions mayalso be implemented, such as restrictions based on GPS locations, Stare,zip code, domain names, etc.

Agent server 206 may also execute software that performs workspace anddocument administration/configuration functions, such as controllinguser or client access, available views, and services based onpermissions granted at the time a user account was created. For example,agent server 206 may perform processes that ensure that the identifier(e.g., UID) for each external userid is configured such that there isonly one account created for each user and also allows for associationto one or more other workspaces.

Agent server 206 may also execute software that performs processes thatprovide, for example: (1) Viewer Services, which provides the abilityfor a reviewer or owner to view content either locally or online; (2)Editor Services, which provides the ability for an owner or reviewer toedit documents or content either locally or online; (3) CompareServices, which may send a request to a server or other computer runningdocument comparison applications to provide the ability to compareversions of content or a selection of text against another selection oftext and return the results of the request; (4) Metadata CleaningService, which may send a request to a server or other computer toprovide the ability to clean default metadata (e.g., documentstatistics, white text, small text, tracked changes and comments) fromdocument content and return the cleaned file to Agent Server 206 forfinal delivery; (5) Information Rights Management Service, which maysend a request to a server or other computer running software to providethe ability to clean content of all default metadata (as describedabove), stamp/encrypt into the document the originating sourceinformation (e.g., Author and Company Names, date and time, etc.) andinformation relating to a user that the document will be sent to intothe property of the document so that the added information cannot beremoved by any metadata cleaning solution and return the clean andstamped file to Agent Server 206 for final delivery; (6) PDF/DigitalSignature (LDF) Service, which may send a request to a server or othercomputer running software to provide the ability to convert a documentto PDF format and insert a digital signature into the document. In oneaspect, if the document is altered in any manner, the software removesthe digital signature and invalidates the document and returns thesigned document to Agent Server 206 for final delivery.

Clients (e.g., 102, 104) that interconnect with collaboration platform110 in system environment 100 may employ a system of components similarto the system disclosed in FIG. 2. In one embodiment, an owner (e.g.,client 102) and a reviewer (e.g., client 104), or multiples thereof, mayeach utilize the components of client device 202, client storage 204,and agent server 206, all interconnected by the same collaborationplatform 110. In accordance with certain embodiments, each user mayshare documents and content as owners by publishing links on a workspaceto collaboration platform 110 through agent server 206 or client device202. Users may then also review and/or edit documents as reviewers byopening the links on a workspace to the shared documents rendered bycollaboration platform 110.

In certain embodiments, reviewers may not need to employ one or more ofa client device 202, client storage 204, or agent server 206. Forexample, the disclosed embodiments may be configured such that areviewer that provides edits, annotations, and/or comments on an owner'sdocument may access links to the document without the use of agentserver 206. As one example, the disclosed embodiments provide forconfigurations where an owner may grant certain reviewers the option toreview linked content via email within, as one example, a browserwindow. Thus, certain embodiments of the disclosed invention may enablereviewers that do not use an agent server 206 to participate incollaborating with owners.

As described, system 100 provides mechanisms that enable one or moreowners to create workspaces containing documents, folders of documents,content, and other information that may be shared over a network withone or more reviewers. Through integration with collaboration platform110, certain embodiments provide a secure manner of providing customizedcollaboration where a reviewer may have access to review and/or editdocuments in a workspace, but may be prevented from obtaining a copy ofthe modified document after a communication session with collaborationplatform 110 ends. The owner's system, however, is configured tosynchronize with the owner's local storage system all changes made byall reviewers (whether done simultaneously or at different times)through collaboration platform 110. Thus, unlike conventional documentsharing systems, where information may be maintained at a web-basedlocation, and overwritten when changes are made, the disclosedembodiments provide methods and systems that securely maintain anoriginal document at the original owner's storage system, along with anysynchronized updated versions of the document. Moreover, through theworkspace concepts disclosed herein, owners can configure and implementcollaboration sessions where content can be selectively shared withoutlosing control of the shared content in the workspace to reviewers. Forinstance, certain embodiments enable collaboration platform 110 topresent documents and/or folders to reviewers via browser (or similarsoftware) executing at the reviewer's client computer, but prevents thereviewer's client computer from maintaining copies of the documents inthe browser's cache memory. Collaboration platform 110's virtual memorymay be configured such that the workspace and documents and foldersrendered by collaboration platform 110 is deleted and not availablefollowing a communication session with a user. These and other aspectsof the disclosed embodiments may be performed by one or more of thecomponents of system 100. The exemplary processes that may be performedby the components are described below.

FIG. 3 is a flowchart of an exemplary workspace creation process 300that may be performed by one or more components of system 100 consistentwith certain disclosed embodiments. In one embodiment, the workspacecreation process 300 may begin with client device 202. For example,process 300 may begin with agent server 206 receiving a request tocreate a workspace from client application 202A (Step 305). Depending onthe type of application, the request may be generated automatically byclient device 202, or it may be generated in response to a user commandwhen running application 202A. For example, application 202A may includean Add-On, menu option, or hot key sequence that initiates a request tocreate a workspace. FIG. 3A shows an exemplary system with a client(e.g., client 102) that includes, among other things, four clientapplications 202A-1 to 202A-4 with “create workspace” options.

Agent server 206 may then provide options to client 202 to present to auser operating client 202 to configure views for the workspace (Step310). In one aspect, embodiments execute processes that render a userinterface window containing selections, menus, options, etc. to enable auser to customize and configure a workspace. For example, agent server206 may provide options to enable a user to select tabs, and areas inworkspace that are specific to a user. For example, agent server 206 mayprovide options for the user to include one or more of the tabsdescribed above in connection with FIG. 1A. In other embodiments, client202 may provide these options to a user operating client 202 forconfiguring a workspace. Agent server 206 may receive input from client202 indicating the configurations and types of views for the workspaceand store the information.

Agent server 206 may also provide options to client 202 to present tothe user operating client 202 to configure reviewer access rights toviews of the workspace (Step 320). In one embodiment, agent server 206may provide options to allow the user to identify and select accessrights to certain views within the workspace for one or more reviewers.For example, a user may allow certain reviewers associated with abusiness entity access to all views in the workspace, while restrictingaccess by other reviewers associated with the same business entity toone or more of the views of the workspace. The disclosed embodimentsalso enable the user to configure access rights based on differentbusiness entity relationships, geographical locations, domain namecharacteristics, and any other type of characteristics relating toreviewers or groups of reviewers. In other embodiments, client 202rather than agent server 206 may provide these access rights options toa user operating client 202.

In certain embodiments, agent server 206 functions as an intermediarybetween client 202 and collaboration 110 in generating workspaces afterconfiguration is complete. In step 323, agent server 206 assigns aunique identifier to the workspace that is provided to collaborationplatform 110. Once the workspace parameters (e.g., access rights, views,and other aspects such as look and feel, controls, tagged with uniqueidentifiers, etc.) are configured, agent server 206 stores the workspaceparameters for later use when the workspace is accessed for rendering bycollaboration platform 110 (Step 325).

FIG. 4 is a flowchart illustrating an exemplary workspace update process400 consistent with certain disclosed embodiments. This workspace updateprocess may be performed by one or more components of system 100. In oneembodiment, an owner (e.g., client 102) may publish a content link to ashared workspace in order to share content for review, annotating,and/or editing by authorized reviewers (e.g., client 104). The owner mayshare various types of content on the shared workspace 150, includingbut not limited to documents, folders of documents, database entries,calendar entries, and any other form of content or information. In oneembodiment, the owner may initiate the workspace update process aftercreating a new document or folders of documents, or after updating adocument through client application(s) 202A.

To share content, the owner may access the workspace, for example, byinitiating a request at client device 202. In one embodiment, agentserver 206 receives the request to access the workspace (Step 405).Agent server 206 may then attempt to identify the owner (Step 410).Agent server 206 may then determine whether the owner is authorized toaccess the workspace based on the user's credentials (Step 415). If so,the process continues to step 420. If not (Step 415; No), agent server206 may initiate a logon process at Step 440, where the agent server 206requests and receives from the owner credentials (e.g., a usernameand/or password) for accessing the workspace. If the owner's usercredentials do not march any authorizations, agent server 206 denies theowner access (Step 445). However, if the owner provides the propercredentials, the process continues to step 420.

At step 420, the owner may then select content (e.g., a document, folderof documents, etc.) from an original storage location in client storage204 to attach to the workspace (Step 420). In one embodiment, clientstorage 204 may perform processes that create a copy of the originalselected document to ensure the original document is maintained in theoriginal source location in client storage 204. Client storage 204 maycreate a collaboration document (see e.g., FIG. 3A) for this purpose.Agent server 206 may then create and store a copy of the content fromclient storage 204 (Step 425). In certain embodiments, softwareprocesses executed in agent server 206 and client storage 204 mayinterface and communicate to facilitate the copying of the selecteddocument to agent server 206. In certain embodiments, client storage204, agent server 206, and/or collaboration platform 110 may eachperform respective processes that create entries in edit history tablesor activity logs maintained by each of these components that provide alog record of the copy operations of the document (or folder ofdocuments). The log record may include a date and timestamp of thetransaction involving the copy of the document (or folder(s)) to agentserver 206 for inclusion in the workspace and the identifier relating tothe client (e.g., client 102) and/or user that initiated thetransaction.

Agent server 206 may then synchronize the newly added document to theworkspace with collaboration platform 110. In one embodiment, agentserver 206 may publish a link to the copy of the document in theworkspace on collaboration platform 110 (Step 430). Agent server 206 mayalso send a notification to authorized reviewer(s) that indicates thedocument has been added to the workspace (Step 435). In one embodiment,agent server 206 may send a notification email to authorized reviewers,alerting them to the presence of the new content available on the sharedworkspace for review and/or editing. In one embodiment, the owner mayinitiate the email notification through client application 202A. Forexample, as shown in FIG. 3A, client application 202A may includemechanisms (ribbon invite options, right-click options, etc.) thatenable a user working with application 202A to invite one or morereviewers to access the document (or folders) that has been added ormodified in the workspace.

In certain embodiments, the email may contain a link to the workspace sothat reviewers may log into the workspace to access the shared contentthrough the published link. In other embodiments, the email may containa link to the workspace provided by collaboration platform 110. Theworkspace rendered by collaboration platform 110 may include a contentlink to the copied document hosted by agent server 206, which may bedisplayed in an editor process (e.g., text editor) for reviewing and/orediting, permitting a reviewer to review and/or edit content in abrowser or web-based format. Thus, in certain embodiments, the sharedcontent may not be stored at collaboration platform 110, but instead thecontent (E.g., documents) are rendered in a web-based format for displayat the reviewer's or on the collaboration platform's browser or similarsoftware. In these embodiments, only a published link passes beyond theowner's client (e.g., client 102) through, for example, a firewall,leaving the owner in sole control over the shared content except for anyauthorizations and access rights provided to one or more reviewers.

In certain embodiments, agent server 206 and/or collaboration platform110 may generate activity entries which are stored in an activity log ofdatabase tables maintained by agent server 206 and/or collaborationplatform 110. Agent server 206 and/or collaboration platform 110 maygenerate these entries whenever a content link is published, notified,accessed, added, saved after editing, closed, or at any other eventselected by a user at the time of creating updating, or editing aworkspace or publishing a content link. In certain embodiments, theentries may store the following items of information for eachtransaction with a content link: date, timestamp, user ID, user emailaddress, or any other item of information pertaining to the owner,reviewer, access rights, or content link. For example, the activityentries may also include information about the content link includingthe linked content's size, owner, version, etc including informationpertaining to any edits or changes made by reviewers or owners.Depending on user authorizations and access rights, collaborationplatform 110 may provide, through agent server 206, access by reviewersto activity logs consistent with various disclosed embodiments of theinvention. Additionally, client storage 204 may create and updateactivity logs when an updated version of shared content is synchronizedconsistent with various disclosed embodiments of the present invention.

For example, agent server 206 and client storage 204 may be configuredto create log entries of the notification in their respective edithistory tables. (See e.g., FIG. 3A, edit history). The log entries mayinclude a date and timestamp of the notification transaction and anidentifier of the user or client that initiated the transaction.Further, agent server 206 may create an activity record of the emailaddress for each recipient of the notification within an invitationtable maintained by agent server 206. Agent server 206 may alsoassociated the notification activity record with the email recordmaintained in the edit history table of agent server 206. Collaborationplatform 110 may also create and store such entries and generateactivity records either alternatively or in tandem with agent server 206and/or client storage 204. In certain embodiments, collaborationplatform 110 may delete all historical data, such as the activityrecords, transaction logs, etc. automatically when a communicationsession ends with a reviewer.

FIG. 5 is a flowchart illustrating an exemplary collaboration reviewprocess 500, consistent with certain disclosed embodiments of thepresent invention. This process may be performed by one or morecomponents of system 100. In one embodiment, a reviewer (e.g., client104) may receive a request to access a workspace from agent server 206of an owner in accordance with the notification processes describedabove in connection with FIG. 4. In one aspect of the disclosedembodiment, a reviewer may initiate a request to collaboration platform110 to access the workspace identified in the notification (or anyworkspace that the user may wish to attempt to access). The process 500may also be performed for owners attempting to access a workspacethrough collaboration platform 110. Collaboration platform 110 mayreceive the request provided by a client (e.g., client 104) over network120 (Step 505).

In one embodiment, the reviewer may initiate the request at clientdevice 202. In another embodiment, a user may open a notification emailand initiate a request to access the workspace through the link in theemail. In certain aspects, agent server 206 of the reviewer clientcomputer may initiate the request via client device 202 of thereviewer's client computer (e.g., client 104). Upon receiving therequest, collaboration platform 110 may attempt to identify the user(Step 510). Collaboration platform 110 determines whether the user isauthorized to access the workspace (Step 515). If so, collaborationplatform 110 may grant the user access to the workspace and the processcontinues to step 520. If not, collaboration platform 110 may initiate alogon process at Step 545, where it requests and receives credentialsfrom the user (e.g., username and/or password). If collaborationplatform 110 determines that the user's user credentials do not matchany authorizations, collaboration platform 110 may deny access (Step550). If the credentials do match, the process continues at step 520where a communication session is established with the user andcollaboration platform 110.

Once the user is authorized, collaboration platform 110 may collect theinformation relating to the requested workspace from agent server 110,and render the workspace with views based on one or more rules that takeinto account the requesting user's access rights previously configuredby the workspace creator. In one example, platform collaborator 110 mayreceive decisions of access rights by agent server 206 associated withthe owner of the workspace that identifies the views and options thatthe user is allowed to receive via collaboration platform 110. Uponsuccessfully accessing the workspace, an authorized user may then reviewthe content, including document links, shared on the workspace pursuantto that user's access rights. The user may, for example, access and viewthe email, calendar, news, history, reporting, activity log, instantmessaging features, links to other workspaces, and tabs, menus,dashboard elements, or graphical displays for other matters, features,or projects. Collaboration platform 110 may receive a request to accesscontent selected by the user (Step 520). The requested content may be arequest to access a document via a content link displayed in theworkspace. In response to receiving an indication that the user selectedone of the document links, collaboration platform 110 may initiate acall to agent server 206 of the document owner to establish a connectionto display the content of the requested document through collaborationplatform 110 (Step 525). In one embodiment, the document and its contentremains at the owner's client 202 or agent server 206 in physicalmemory, and the collaboration platform 110 renders the content invirtual memory, for example via web-based display technologies to abrowser or similar software at the reviewer's client system. In certainembodiments, the memory component of collaboration platform 110 may notbe accessible to the reviewer or owner users and all documents andfolders, content, etc. maintained in virtual memory is deleted from thecollaboration platform 110 at the end of a communication session withthe reviewer or owner user. Collaboration platform 110 may render therequested document, folder, or content at the reviewer's browser, suchthat the rendered information is not stored in the cache or temporarymemory of the reviewer's browser.

Based on the access rights for the requested content, collaborationplatform 110 may provide application services through the web-basedservice such that the reviewer may view the shared content displayedthrough a virtual memory by the collaboration platform 110 (Step 525).In certain embodiments, collaboration platform 110 may display thecontent with a text and/or data editor having functionalities similar tothose offered by client application(s) 202A, permitting the reviewer toreview, annotate, and/or edit the content in accordance with the user'saccess rights (Step 530). The virtual memory display may disable anycopy, save, and print functions to prevent reviewers 104 from obtainingcontrol over any part of the displayed content. Collaboration platform110 receives input from reviewers 104 regarding any changes to thecontent (e.g., changes to text in a document, etc.) and maintains invirtual memory the changes in accordance with the document editingfeatures offered by the platform. Collaboration platform 110 may receivean indication once the reviewer has completed collaboration activities(e.g., log off), and in response closes the communication session withthe reviewer (Step 535). Collaboration platform 110 may initiatesynchronization processes with agent server 206 of the owner to provideactivity information and changes to agent server 206 (Step 540). Oncesynchronization is complete, collaboration platform 110 may selectcontent from the virtual memory, including all information relating tothe requested, viewed, and edited content for the reviewer's workspace(Step 545). In one embodiment, a container is provided fromcollaboration platform 110 to agent server 206 over network 120 beforethe collaboration platform 110 deletes the information relating to thecontent. In another embodiment, agent server 206 may receive anindication that synchronization is required and retrieves the updatedinformation over network 120 before deletion by the collaborationplatform 110.

FIG. 6 is a flowchart illustrating an exemplary synchronization process600 consistent with disclosed embodiments. In one embodiment, agentserver 206 may receive synchronization information from collaborationplatform 110 following a collaboration session with a reviewer, such asthat described above in connection with FIG. 5. Agent server 206 mayreceive the updated content for a document or set of documents (Step610) and save a copy of the content and changes in memory (Step 615). Inone embodiment, agent server 206 saves each change as an individualdatabase object to a Changes Table that is associated with the emailaddress of the Reviewer that made the changes. Agent server 206 may alsocreate an activity entry to log the save operation to the Edit HistoryTable in an agent server 206 database with the date and timestamp of thetransaction, along with the email address of the reviewer that initiatedthe transaction.

Agent server 206 may then synchronize the changes with client storage204 (Step 620). In one embodiment, agent server 206 communicates withclient storage 204, which creates a new document version (CollaborationDocument) associated with the original document that was edited, whichmay or may not be in a proprietary file format, and sets security accessrights to client storage 204 Userid relating to the original transactionthat created the document or content. Agent server 206 may thensynchronize the changes to the created Collaboration Document and createseveral activity entries to (1) log the create operation to a versionstable, (2) log the save operation to the edit history table with thedate and timestamp of the transaction using the Userid from the originaltransaction, and (3) log the email address of the reviewer that made thechanges to the document. Client storage 204 also logs the save operationin its edit history table with the same date and timestamp and Useridinformation, and logs the create operation in corresponding versiontable maintained by client storage 204. In some embodiments, clientstorage 204 or agent server 206 may further harmonize multipleCollaboration Documents corresponding to the changes, such asannotations, edits, etc. of various reviewers, generating a MasterDocument incorporating the alterations and edits from each CollaborationDocument, for example in redline or other editing format, to provide anowner with a comprehensive version for review.

In certain embodiments, after agent server 206 has synchronized theupdated content to client storage 204, agent server 206 may republishthe content link on the workspace for subsequent access by authorizedreviewers, enabling full or partial bi-directional synchronizationbetween the content stored at client storage 204 and the content linkson workspace 150 that is rendered by collaboration platform 110. Incertain embodiments, this republished link may display the updatedversion with changes in redline, or in other embodiments withoutredline. Thus, the republished link may provide display the MasterDocument, or in other embodiments multiple links may display variousCollaboration Documents reflecting the annotations and edits of certainreviewers 104. Collaboration platform 110 may also provide services thatenable reviewers to view changes to a shared document made by multiplereviewers (and the owner) in real-time. Thus, in certain embodiments,collaboration platform 110 may enable reviewers to access the latestversions of content by automatically republishing links whenever thelinked content is updated. Additionally, collaboration platform 110 mayprovide notifications, such as emails or other messages, to reviewerswho have a linked document open in virtual memory when that document isupdated by another user and a link is republished, providing options tosynchronize the updates with the reviewer's current alterations,annotations, edits, or other changes.

In other embodiments, agent server 206 may be configured to present therepublishing of content links based on parameters set by an owner of adocument. For example, if a document owner 102 does not wish forreviewers to access each other's edits and alterations until the ownerreviews them, agent server 206 may allow the owner to manually republisha link to the document. As another example, agent server 206 may beconfigured to allow an owner 102 to suspend or lock a document fromfurther editing, or delete the link from a workspace. Agent server 206may also be configured to enable the owner 102 to reopen editing andreview of a document by allowing the owner 102 to manually republish alink to continue the collaborative process. In another embodiment, if anowner 102 decides that enough editing has occurred and that review iscomplete, the owner may then use features provided by agent server 206to republish a link using, for example, an Approved Content option of aworkspace. Agent server 206 may also allow an owner to provide a link tosolicit final approval or comments from reviewers 104 through anapproval process that may be executed by components of system 100consistent with certain disclosed embodiments.

With certain information or documents, owners may desire to share theirown latest available updates in real time with various reviewers. Inaccordance with certain embodiments of the invention, agent server 206and/or client storage 204 may be configured with software that whenexecuted automatically updates workspaces whenever content is updated ina document by an owner. For example, upon completion of changes to adocument via client application 202A, client device 202 may notifyclient storage 204 that a change was made to the document. In response,client storage 204 may initiate synchronization processes where aCollaboration Document is created that corresponds to the originaldocument (see e.g., FIG. 3A) and the changes are synchronized with agentserver 206 for updating the links for that document in any appropriateworkspaces.

As described above, certain disclosed embodiments permit single ormultiple owner(s) (e.g., client 102) and single or multiple reviewer(s)(e.g., client 104) to connect to collaboration platform 110 for sharingdocuments, folders of documents, content, etc., in various combinationsof shared workspaces. Certain embodiments also provide for thebi-directional synchronization of, for example, documents between theclient storage 204 and agent server 206 of an owner (e.g., client 102)with the document links published to the workspaces on collaborationplatform 110, such that reviewers (e.g., client 104) that accessdocument links included in the workspace may access up-to-date content,and owners accessing documents stored on their own systems (e.g., client102) may also have access to up-to-date content. In further embodiments,owners may configure user authorizations and access rights, limiting therights of reviewers to maintain security and control over the owners'documents. In still further embodiments, the disclosed embodiments mayhost and provide various other applications and functionalities inconjunction with the collaboration, synchronization, and securitysystems and processes described above.

Other embodiments will be apparent to those skilled in the art fromconsideration of the specification and practice of the featuresdisclosed herein. Further, the sequence of processes steps disclosed inconnection with the figures is not intended to be limiting. Additionalor fewer steps may be implemented in a manner consistent with certainfeatures of the disclosed embodiments. In some embodiments, an owner 102may configure a workspace 150 at client 202 or client application 202A,and the client 202 may then provide input to agent server 206 to storethe workspace parameters for use when the workspace 150 is accessed forrendering by the collaboration platform 110. An owner 102 may then,consistent with certain embodiments, share content over the workspace150 by publishing links to copies of documents stored in at agent server206. In order to view, annotate, and/or edit shared content, reviewers104 may then access the workspace 150 through a client 202 or through alink in a notification email and access document links consistent withindividual access rights. As one example of this process, the agentserver 206 may function as a transitional content repository, with thecollaboration platform 110 displaying in virtual memory the contentstored in physical memory at the agent server 206. The collaborationplatform stores no information or data related to the accessed content,temporary or otherwise, that is accessible to any owner 102 or reviewer104. Reviewers 104 may then view, annotate, and/or edit the contentwithin the virtual memory, closing the content when the session iscomplete.

Consistent with certain embodiments, the collaboration platform 110 maythen send the updated content to the agent server 206 via a container,or the agent server 206 may retrieve the updated content from thecollaboration platform 110. After this exchange, the collaborationplatform 110 closes the content and deletes all information and datarelated to the content. The agent server 206, having received theupdated content, may then save it as a Collaboration Document in acollaboration file format such as, for example, as a Litera .ids file.The agent server 206 may then synchronize this new CollaborationDocument file with the client storage 204, and either the agent server206 or client storage 204 may incorporate various updated versions intoa Master Document containing all updates, which may enable an owner 102to efficiently review all annotations and edits at once. Consistent withcertain embodiments, the agent server 206 may then automaticallyrepublish a document link, providing access to the Master Document, aCollaboration Document, the original unaltered document, or somecombination of these depending on the various access rights andconfigurations established for the document and/or the workspace 150.Accordingly, certain embodiments may provide for bi-directionalsynchronization at the owner (e.g., client 202 and/or client storage204) and reviewer levels (workspace 150), such that the owner(s) andreviewers) each have access to the most current and up-to-date content.

Owners and authorized reviewers may also configure varying access rightsconsistent with certain embodiments of the disclosed invention.Depending on access rights and configurations, each owner 102 andreviewer 104 may have access to links providing access to differentversions of the content; for example, one reviewer 104 may be able toaccess the Master Document while other reviewers 104 may only haveaccess to the original unaltered document or perhaps may not receive arepublished link at all. In other embodiments, an owner 102 may selectaccess rights and configurations to prevent automatic republishing oflinks, which may provide the owner 102 an opportunity to review anyupdates before deciding whether to share them. At each step of thevarious processes described herein consistent with various embodimentsof the claimed invention, including accessing content, sharing contentvia links, saving content, synchronizing content, etc., one or morecomponents of client 102, 104 may create and save activity log entriesincluding information such as a timestamp, userid, user contactinformation, edit history, among others.

To further illustrate certain aspects of the disclosed embodiments,consider an example where an owner uses a word processing application(e.g., 202A) to create a workspace via an option provided as an Add-onor a hot key sequence in the application. The owner may create theworkspace (called Workspace 1 for illustration purposes). Using theworkspace configuration features of the disclosed embodiments, the ownermay assign user 1, user 2, and user 3 with certain access rights to theworkspace. The owner creates and links a document having a formatassociated with the word processing application (called document“222.doc” for illustration purposes). Once completed, the workspaceconfiguration information set by the owner is sent to agent server 206,which takes and maintains a copy of document 222.doc in local memory.Agent server 206 enables the owner to set access rights for one or morereviewers of document 222.doc. In this example, the owner allows users 1and 2 to have viewing and editing rights to document 222.doc and onlyallows user 3 to have viewing rights to document 222.doc. Onceconfigured, agent server applies the permissions to the view fordocument 222.doc in Workspace 1.

At some point, users 1, 2, and 3 may receive notifications via agentserver 206 or client application 202A, that document 222.doc isavailable in Workspace 1, and thus accesses collaboration platform 110through their respective browsers (or similar software). For each user,collaboration platform 110 may create Workspace 1 in a web-based formatusing virtual memory. In this example, collaboration platform 110 maygenerate a workspace content that includes a folder called “Workspace 1”that corresponds to the workspace created by the owner. Agent server 206publishes the document 222.doc as a content link in Workspace 1, whichis rendered by collaboration platform 110. Because, in this example, theowner only provided access rights to users 1-3, any other users whoaccess the workspace via collaboration platform 110 will not see thefolder “Workspace 1.”

Each user (users 1-3) may click on the Workspace 1 folder link renderedby collaboration platform 110 to view the content in the folder. In thisexample, a content link to document 222.doc may be displayed. As eachuser clicks on the content link for document 222.doc, the collaborationplatform 110 through agent server 206, automatically updates statusfields in the workspace, such as “under review,” etc. Aspects of thedisclosed embodiments enable agent server 206 to populate the list ofcontent links to documents rendered by collaboration platform 110. Inthis way, collaboration platform 110 may be connected to agent server206, but not with the data storage 204 that hosts the original document222.doc. Thus, in certain aspects, agent server 206 may act as aclearinghouse for all permissions, access rights, etc. for the contentand documents in Workspace 1. When, for example, user 1 views and clickson the content link for document 222.doc, collaboration platform 110provides for the link to be directed to agent server 206, which allowsthe content to open in the browser of user 1. In one embodiment,document 222.doc may not be rendered in user 1's browser as the wordprocessing application document. Instead, the document 222.doc may beconverted into HTML or other formats that user 1's browser is configuredto accept and present.

FIG. 7 shows an exemplary block diagram of a system involvingcollaboration processes consistent with certain disclosed embodiments.In the example shown in FIG. 7, reviewer 1 (user 1), reviewer 2 (user2), and reviewer 3 (user 3) receive notifications including links toworkspace 1 that provides access to workspace 1 rendered bycollaboration platform 110. FIG. 7 also shows workspace 1 including thefolder “workspace 1” which provides a link to all documents included inthat folder, which in this example, includes a content link to document222.doc. When selected, the content link to 222.doc links to the copy ofdocument 222.doc maintained by agent server 206. FIG. 7 also shows datastorage 204 at the owner that maintains the original document 222.doc,which is separate from any connections to collaboration platform 110.

Upon completion of edits by user 1 via user 1's browser, user 1 mayclose the document via collaboration platform 110. In response,collaboration platform 110 may provide the content including the changesmade by user 1 to agent server 206. Agent server 206 may then convertthe document 222.doc into another format, such as a Litera IDS format(222.IDS) or other formats usable by the owner's client system. Agentserver 206 may then log the changes for user 1. Agent server 206 maysynchronize the user 1 changes with data storage 204 to create asecondary file (e.g., a collaboration document) for user 1. Secondaryfiles are created for each reviewer (e.g., user 1 and user 2) thatcreated changes to the document. In certain embodiments, the secondaryfile may include for each reviewer the changes for each paragraph orportion of document 222.IDS. Once synchronized, collaboration platform110 may delete the document content from its virtual memory. In otherembodiments, collaboration platform 110 may delete the document content(and any other related information) from its virtual memory when agentserver 206 receives the changes to document 222.doc and thecommunication session with user 1 is closed. The sessions betweencollaboration platform 110 and user 1 and user 2 may take placesimultaneously or at different times.

FIG. 8 shows an exemplary block diagram of collaboration synchronizationprocesses consistent with certain disclosed embodiments. FIG. 8 shows acollaboration environment relating to system 100 where reviewer 1creates changed text 752 to original text 750 of document 222.docrendered in workspace 1 for reviewer 1 during a communication sessionbetween collaboration platform 110 and reviewer 1's client system. FIG.8 also shows reviewer 2's changed text 754 to original text 750 ofdocument 222.doc that is rendered in workspace 1 for reviewer 2 during acommunication session between collaboration platform 110 and reviewer2's client system. The changed text for each reviewer (e.g., changedtext 752 and 754) is provided to agent server 206 for creation of aseparate document in a different format than the original document'sformat. In this example, reviewer 1 document 222.IDS is created toreflect the changes made by reviewer 1 to original text 750 of document222.doc and reviewer 2 document 222.IDS is created to reflect thechanges made by reviewer 2 to original text 750 to the original text 750of document 222.doc. FIG. 8 also illustrates the result ofsynchronization between agent server 206 and data storage 204 such thata secondary file, reviewer 1 222.IDS, is created and maintained by datastorage 204 and a secondary file, reviewer 2 222.IDS, is created andmaintained by data storage 204. In one embodiment, data storage 204 mayexecute processes that combine the information included in the secondaryfiles to create and maintain a secondary file, 222.IDS, which reflectsthe original text 750 and all changes to the text (e.g., 752 and 754) oforiginal document 222.doc. In another embodiment, data storage 204 mayenter the information included in the secondary files into a databasethat reflects the original text 750 and all changes to the text (e.g.,752 and 754) of original document 222.doc such that the changes arestored separate from but parallel to the original document 222.docitself. The corresponding application executed by the owner's clientsystem (in this example a Litera IDS application) may be used by theowner to perform review of the changes stored in a secondary file (e.g.,222.IDS) or in a separate database. In one aspect, those changes may beviewed and processed in a manner consistent with the features disclosedin U.S. Pat. No. 7,818,678, entitled “Collaborative Document Developmentand Review System,” issued Oct. 19, 2010, the disclosure of which isherein incorporated by reference in its entirety.

Certain embodiments may also be implemented that use other formats thanthe .IDS format described above in connection with FIG. 8.

In certain aspects, as long as the owner does not close the originaldocument 222.doc, users may collaborate and make changes to the documentwithout overriding other user changes through the collaboration platform110. Thus, data storage 204 may maintain a converted document, 222.IDSmaintained by data storage 204 will contain both user 1 and user 2changes as long as the owner does not lock the document from furtherediting (that can be done at anytime) which would change the statusfiled to “review complete” in workspace 1. If at that time, the ownerdoes close the original document, review is complete and the underlyingnew formatted application (e.g., IDS application in this example) mayallow the owner to publish the document as a new version (e.g., document222.1.doc). This process allows the owner to receive changes fromauthorized reviewers (e.g., user 1 and user 2), but also enable anotheruser (e.g., user 3) to later review it. In this example, the owner maypublish the document as a new version (e.g., 222.1.doc) and thecollaboration process may continue with user 3 having access to thedocument via collaboration platform 110. Accordingly, certainembodiments enable bi-directional synchronization between the owner(s)and reviewer(s).

As explained above, the owner is able to review the changes made byreviewers using, for example the Litera IDS features described in U.S.Pat. No. 7,818,678. Moreover, in one embodiment, collaboration platform110 may be configured to provide editing features that provide similarreview and collaboration features disclosed by U.S. Pat. No. 7,818,678.

The disclosed embodiments may be implemented in a number of environmentsto facilitate collaborations in real time over the Internet wherecontrol is retained by an owner over created documents and content. Forexample, owners may restrict the rights of reviewers to single-accesssessions, where after a reviewer completes a communication session wherethey access and possible edit documents via a link on a workspace thelink may be deleted—not updated and republished. In other embodiments,owners may restrict the rights of reviewers by only permitting access tostatic links, where reviewers may access links to the version of adocument originally shared by an owner on the workspace, but this linkmay not be updated and republished as owners and reviewers with greateraccess rights update the document over time. In still other embodiments,owners may permit reviewers to annotate or edit content, and may permitcertain reviewers to review other certain reviewers' annotations andedits, but may quarantine other reviewers by denying them access toreview certain reviewers' annotations and edits. Thus, owners may createand generate highly individualized combinations of access rights toachieve various purposes, whether security-based, work quality-based, orotherwise.

Various disclosed embodiments of the present invention may also beimplemented in different interactive contexts. For example, certainembodiments may be utilized to streamline medical record sharing in asecure environment. Currently, many doctors and hospitals maintain theirown files, and sharing files requires requests between institutions.This often involves a transmission delay, hampering the health care ofpatients as they will often need to schedule follow-up appointments dueto the delay in sharing, reviewing, and acting on medical informationoriginating from remote locations. With certain disclosed embodiments ofthe present invention, a doctor or a doctor's staff may set up aworkspace for a given patient. The doctor and patient may operate asboth owners 102 and reviewers 104 of medical records and otherinformation shared over the workspace on the collaboration platform 110.If a patient later sees a new doctor, the patient may be able to grantthe new doctor access to the workspace as a new reviewer 104. Dependingon the new doctor's access rights, the new doctor may then shareadditional medical records and information and access pre-existingrecords. As a result, all doctors with access to the patient's workspacemay access the latest updated versions of the patient's healthcarerecords to provide the most current and up-to-date care. Furthermore,doctors may collaborate over a patient's workspace via email ormessaging, through making and sharing calendar entries, or by commentingon, annotating, and/or editing linked medical records. The patient, bysetting access rights, may remove certain doctors as reviewers 104 whenthe patient is no longer seeing those doctors and otherwise maintaindesired levels of confidentiality and restricted access. Additionally,the patient may provide access to various family members, guardians, orother trusted individuals. By utilizing various disclosed embodiments ofthe present invention, access to medical records may shift from thecurrent health center-oriented system to a patient-centric system.

Certain embodiments may also be utilized in an educational context,facilitating teachers and students in sharing ideas and information overa collaboration platform 110 in a safe and secure system, but allowingthe educators to prevent the students from obtaining copies of originaldocuments through collaboration platform 110. Still other embodimentsmay enable law firms and their clients to share documents for reviewing,signing, editing, etc. while retaining control over their own sharedcontent. Still others may enable various distinct law enforcementagencies, for example state and federal entities, to collaborate andshare information regarding an investigation over a shared and secureworkspace 150. Consistent with certain embodiments, the disclosedinvention may also create, enable and/or provide various customized orindustry-specific templates to further enhance collaboration.

In these or any other interactive contexts, multiple collaborationplatforms 110 may be implemented that provide collaboration featuresconsistent with the disclosed embodiments between the same or differentowners and/or reviewers. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the disclosed embodiments being indicated by the following claims.

1-50. (canceled)
 51. A computer-based system for collaboratinginformation over a network, comprising: a collaboration platform; andone or more processors configured to: generate a collaboration document,the collaboration document being a copy of an original document createdby an owner, provide content of the collaboration document to thecollaboration platform, wherein the collaboration platform temporarilyrenders the content of the collaboration document to a first reviewer,receive, from the collaboration platform, an adjustment to the renderedcontent of the collaboration document made by the first reviewer throughthe collaboration platform during a communication session, update thecollaboration document by synchronizing the adjustment made by the firstreviewer to the rendered content of the collaboration document with thecollaboration document, such that the original document remainsunadjusted.
 52. The computer-based system of claim 51, wherein thecollaboration platform temporarily stores the content of thecollaboration document in a virtual memory for rendering the content ofthe collaboration document to the first reviewer.
 53. The computer-basedsystem of claim 51, wherein the one or more processors are furtherconfigured to: provide content of the collaboration document to thecollaboration platform, wherein the collaboration platform temporarilyrenders the content of the collaboration document to a second reviewer,receive, from the collaboration platform, an adjustment to the renderedcontent of the collaboration document made by the second reviewerthrough the collaboration platform during a communication session, andupdate the collaboration document by synchronizing the adjustment madeby the second reviewer to the rendered content of the collaborationdocument with the collaboration document, such that the originaldocument remains unadjusted.
 54. The computer-based system of claim 53,wherein the rendered content of the collaboration document includes theadjustment made by the first reviewer.
 55. The computer-based system ofclaim 53, wherein the rendered content of the collaboration documentomits the adjustment made by the first reviewer, according to an accessrights policy for the second reviewer.
 56. The computer-based system ofclaim 51, wherein the one or more processors are further configured tonotify the first reviewer or a second reviewer that the collaborationdocument is available for review.
 57. The computer-based system of claim51, wherein the one or more processors are further configured to updatethe collaboration document by synchronizing an adjustment made by theowner to the original document with the collaboration document.
 58. Thecomputer-based system of claim 51, wherein the collaboration platformtemporarily renders the content of the collaboration document to a firstreviewer within an application used to create the original document. 59.The computer-based system of claim 51, wherein the one or moreprocessors are further configured to generate a workspace designatingone or more reviewers with access rights to review the collaborationdocument, wherein the workspace indicates the status of the review ofthe collaboration document.
 60. A method for collaborating informationover a network, comprising: generating a collaboration document, thecollaboration document being a copy of the original document, providingcontent of the collaboration document to the collaboration platform,wherein the collaboration platform temporarily renders the content ofthe collaboration document to a first reviewer, receiving, from thecollaboration platform, an adjustment to the rendered content of thecollaboration document made by the first reviewer through thecollaboration platform during a communication session, updating thecollaboration document by synchronizing the adjustment made by the firstreviewer to the rendered content of the collaboration document with thecollaboration document, such that the original document remainsunadjusted.
 61. The method of claim 60, wherein the collaborationplatform temporarily stores the content of the collaboration document ina virtual memory for rendering the content of the collaboration documentto the first reviewer.
 62. The method of claim 60, further comprising:providing content of the collaboration document to the collaborationplatform, wherein the collaboration platform temporarily renders thecontent of the collaboration document to a second reviewer, receiving,from the collaboration platform, an adjustment to the rendered contentof the collaboration document made by the second reviewer through thecollaboration platform during a communication session, and updating thecollaboration document by synchronizing the adjustment made by thesecond reviewer to the rendered content of the collaboration documentwith the collaboration document, such that the original document remainsunadjusted.
 63. The method of claim 62, wherein the rendered content ofthe collaboration document includes the adjustment made by the firstreviewer.
 64. The method of claim 62, wherein the rendered content ofthe collaboration document omits the adjustment made by the firstreviewer, according to an access rights policy for the second reviewer.65. The method of claim 60, further comprising notifying the firstreviewer or a second reviewer that the collaboration document isavailable for review.
 66. The method of claim 60, further comprisingupdating the collaboration document by synchronizing an adjustment madeby the owner to the original document with the collaboration document.67. The method of claim 60, wherein the collaboration platformtemporarily renders the content of the collaboration document to a firstreviewer within an application used to create the original document. 68.The method of claim 60, further comprising generating a workspacedesignating one or more reviewers with access rights to review thecollaboration document, wherein the workspace indicates the status ofthe review of the collaboration document.
 69. A computer-based systemfor collaborating information over a network, comprising one or moreprocessors configured to: receive a request from a first reviewer toaccess the content of a collaboration document, wherein thecollaboration document is a copy of an original document, initiate acommunication session with the first reviewer, retrieve content of thecollaboration document, store the content of the collaboration documentin a virtual memory, temporarily render the content of the collaborationdocument to the first reviewer, receive an adjustment made by the firstreviewer to the rendered content of the collaboration document, generateinformation for synchronizing the adjustment made by the first reviewerto the rendered content of the collaboration document with thecollaboration document, and terminating the communication session withthe first reviewer.
 70. The computer-based system of claim 69, whereinthe one or more processors are further configured to: receive a requestfrom a second reviewer to access the content of a collaborationdocument, initiate a communication session with the second reviewer,retrieve content of the collaboration document, store the content of thecollaboration document in a virtual memory, temporarily render thecontent of the collaboration document to the second reviewer, receive anadjustment made by the second reviewer to the rendered content of thecollaboration document, generate information for synchronizing theadjustment made by the second reviewer to the rendered content of thecollaboration document with the collaboration document, and terminatingthe communication session with the second reviewer.
 71. Thecomputer-based system of claim 70, wherein the rendered content of thecollaboration document includes the adjustment made by the firstreviewer.
 72. The computer-based system of claim 70, wherein therendered content of the collaboration document omits the adjustment madeby the first reviewer, according to an access rights policy for thesecond reviewer.
 73. The computer-based system of claim 69, wherein theone or more processors are further configured to generate a notificationto the first reviewer or a second reviewer that the collaborationdocument is available for review.
 74. The computer-based system of claim69, wherein the one or more processors are further configured to:receive an original document from an owner, and generate a collaborationdocument, the collaboration document being a copy of the originaldocument.
 75. The computer-based system of claim 69, wherein the one ormore processors are further configured to temporarily render the contentof the collaboration document to a first reviewer within an applicationused to create the original document.
 76. The computer-based system ofclaim 69, wherein the one or more processors are further configured toreceive or generate a workspace designating one or more reviewers withaccess rights to review the collaboration document, wherein theworkspace indicates the status of the review of the collaborationdocument.